home *** CD-ROM | disk | FTP | other *** search
- Path: news.primenet.com!not-for-mail
- From: gbe@primenet.com (Gary Edstrom)
- Newsgroups: comp.lang.c++
- Subject: Re: Can anyone explain ?
- Date: 10 Feb 1996 08:50:02 -0700
- Organization: Sequoia Software
- Sender: root@primenet.com
- Message-ID: <311cbd5e.812670142@news.primenet.com>
- References: <823907577.10880@le-vamp.demon.co.uk>
- X-Posted-By: ip049.lax.primenet.com
- X-Newsreader: Forte Agent .99d/32.182
-
- Kurt@le-vamp.demon.co.uk (Kurt Frary) wrote:
- >A) can someone give me some decent comments for the code ?
-
- >B) What the difference between
- > Regs.w.ax - I have only a guess that this will load ax with
- >whatever 32 bit code, or am I being a lamer ?
- >and Regs.h.bl - Load bl with whatever 16 bit ?
-
- Regs.w.ax = 0x0300 is equivilant to the assembly code "mov ax,1"
- Regs.h.bl = 0x10 is equivilant to the assembly code "mov bl,10H"
-
- You should look in the appropriate C header file for the exact definition of
- the REGS structure. It is part of setting up the processor registers for an
- assembly language type call to the operating system. The "Regs.w" format
- addresses the word wide registers, while "Regs.h" addresses the byte wide
- registers. This definition is made with a union because the two groups of
- registers overlap to a certain extent.
-
- >C) How do i know how many parameters to pass to int386x ? i.e. Sregs,
- >regs e.t.c.
-
- You need to get an MS-DOS reference book that includes entry points for DOS any
- ROM BIOS functions you may be calling.
-
-
- --
- Gary Edstrom <gbe@primenet.com> | Sequoia Software
- PO Box 9573 | Programming & Technical Services
- Glendale CA 91226-0573 | PGP Key ID: 0x1A0D44BD
- PGP Fingerprint: 72 AA 4F 73 05 53 89 C6 8A EE F4 EE D1 C0 13 8D
-